System and Method for Providing Healthcare Related Services

ABSTRACT

A system and a method for receiving, by a processing device, a call from a communication device associated with a patient, the communication device associated with a patient having a unique identifier; associating, by the processing device, the unique identifier with a personal health profile stored in a database; determining, by the processing device, a communication device associated with a health care provider; transmitting the personal health profile to a communication device associated with a health care provider; and communicatively connecting the call from the communication device associated with the patient with the communication device associated with the health care provider.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit, pursuant to the provisionsof 35 U.S.C. 119, of U.S. Provisional Application Ser. No. 61/534,109,titled “System and Method for Providing Healthcare Related Services”,filed on Sep. 13, 2011, which is herein incorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to a system and a method forproviding various health care related services to the patients and thehealth care providers, more particularly to an enhanced system andmethod for receiving and managing patient communication to health careproviders.

BACKGROUND OF THE INVENTION

Currently, medical professionals frequently utilize conventionalanswering services to handle calls received from patients, particularly,those received after-hours. In fact, as the volume of calls increases,answering service systems have become necessary for doctors,practitioners, and other medical professionals who want to provide theirpatients with the optimal care and service both during and afterbusiness hours. However, such conventional answering services providebasic support such as operators answering patient calls on behalf of thedoctor or other medical professionals, taking messages on their behalf,forwarding the calls to the medical professionals or paging the medicalprofessionals in cases of emergencies. These existing services areancient and add no value to the health care providers. The servicesmerely function to receive the patient's call and act as a go between tocontact the medical professional. The patient calling these conventionalanswering services can only provide their contact information and waitfor a response from the medical professional. Also, the medicalprofessional does not have access to the patient's health data when heor she is speaking to the patient seeking medical advice. Furthermore,the conversation between the patient and the medical professional duringthe call can be billable events, however, the health care providersdon't typically capture such events since there is no detailed record ortranscript of the calls.

Thus there is a need for an improved system and method to overcome thedeficiencies of the conventional answering services and provide the manyservices that are needed in the health care industry in order to receiveand manage patient communication to the health care providers.

SUMMARY OF THE INVENTION

Embodiments of the present invention are directed to an enhanced systemand method for receiving and managing communication between the patientand the health care providers. The method includes receiving thepatient's call, retrieving patient's profile information, and forwardingthe profile information to the appropriate health care provider (HCP)prior to routing the call to the HCP 108. The method also includesrecording the conversation of the call between the patient and thedoctor, transcribing the call and creating an electronic record of thecall with the corresponding transcript upon which an informal decisionas to whether or not to bill for the call can be made. The methodfurther includes filling the forms for billed calls, and submitting theform along with the record, transcript and bill to the insurancecompany. Thus, billable events are identified and captured based on therecords created and submitted for billing by the system and method ofthe present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more readily understood from the detaileddescription of exemplary embodiments presented below considered inconjunction with the attached drawings, of which:

FIG. 1 is an exemplary block diagram of a system for providinghealthcare related services to a patient in accordance with anembodiment of the present invention;

FIG. 2 is a flow diagram of an exemplary method for receiving andmanaging patient communication to a health care provider, according toan embodiment of the present invention;

FIG. 3 is a flow diagram illustrating exemplary methods for providinghealthcare related services to a health care provider utilizing the datacollected in FIG. 2, according to an embodiment of the presentinvention;

FIG. 4 is a block diagram illustrating a patient management system,according to an embodiment of the present invention; and

FIG. 5 is a block diagram illustrating a computer system that mayperform one or more of the operations described herein.

It is to be understood that the attached drawings are for purposes ofillustrating the concepts of the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a block diagram of an exemplary environmentcomprising a healthcare communication management system (HCMS) 112implemented by a computing device such as a server for providinghealthcare related services in accordance with an embodiment of thepresent invention. As used herein, the term “computing device” isintended to include a programmable electronic machine that performsexecutes software to perform several operations such as assemble, store,correlate, or otherwise processes information. In the exemplaryenvironment, there is a network 102, which may be any type ofcommunications medium that allows for communication between the HCMS112, a patient 104, and a health care provider (HCP) 108. As usedherein, the term “patient” refers to a person in need for a health careservice that calls or communicates with the HCP. It is noted that theterms “caller” and “patient” are used interchangeably. Further, onehaving ordinary skill in the art will appreciate that the caller may beacting as a proxy for the patient.

As used herein, the term “health care provider” is intended to include aprimary physician, on-call physician, physician assistant, nursepractitioner or other health care professionals eligible to provide thehealth care service to the patients. It is noted that the term“physician” is used as the HCP, however, it will be understood that theHCP can by any health care professional as mentioned above. Further, thepatient's HCP or on-call HCP is used interchangeably. As used herein,the term “health care service” is intended to include a means forservice, supplies and procedures for the diagnosis, prevention,treatment, and management of a health condition, illness, injury ordisease.

The HCMS 112 includes any suitable communication device including alandline device, a wireless device and/or an Internet that allows forcommunication with any type of consumer device. The HCMS 112 isconformed to communicatively connect to a plurality of patient devices106 operated by the plurality of patients 104 via the network 102 (e.g.the internet, or the wired or wireless telephone network). The patientdevices 106 can be any device capable of communicating to the HCMS 112via the network 102 including, but not limited to landline, telephone, awireless device, and any computing device. In an exemplary embodiment,the patient device 106 is a mobile device (for example a handheld deviceor a smart phone) that communicates with the network 102 via a wirelessconnection. Pluralities of different HCPs 108 are also connected to thenetwork 102 via various provider devices 110 such as for example, alandline telephone, a wireless device, and a personal computer. In anexemplary embodiment, the provider device 110 is a mobile device (forexample a handheld device or a smart phone) that communicates withnetwork 102 via a wireless connection.

The HCMS 112 includes a computing device 113 that executes a computersoftware program that is configured to perform the functions of arelevant content algorithm, which will be described below. The HCMS 112also includes a communications device (not shown), for connecting to thenetwork 102 to communicate with the patient devices 106 and the providerdevices 110. The HCMS 112 includes a database 114 configured to storepatient profile information. In the preferred embodiment, the termpatient profile information is intended to include a patient'sidentification data, personal data, health history data and othermiscellaneous data related to the patient 104. The HCMS 112 functions toprovide various services on behalf of the HCP 108. As used herein, theterm “health history” includes a comprehensive collection of medicalhistory data including information such as existing diseases, previoushealth problems, injuries, medications and surgical procedures.

Some of these services include answering calls of the patient 104,retrieving patient profile information from the database 114, andproviding this patient profile information to the HCP 108 prior toforwarding the call to the HCP 108. The HCMS 112 also includes arecording device 116 configured to record content of conversation duringa call between the patient 104 and the HCP 108. Any suitable deviceknown in the art may be used, including but not limited to mechanicaltape, optical recorders, digital recorders, silicone chip basedrecording devices, and hard drive storage. Further, the HCMS 112includes a voice recognition device 118 such as dragon, google voice,etc. which functions to transcribe the recorded conversation which istransmitted to the HCP 108 via the device 110. The HCMS 112 furtherincludes a hard drive 120 for storing information such as greetings andrecorded conversations.

The HCMS 112 also includes a patient portal (PP) 436 (shown in FIG. 4)which serves as a secure repository for the patent's 104 medical data.The PP 436 provides access to a registered patient 104 to log in andfill in their patient profile information. It also allows the patient104 to upload any medical data and reports which are securely stored inthe database 114, to be accessed only by the patient 104 and the HCP108. Alternatively, the HCP 108 may sign off and approve the uploadingof such data and reports. The PP 436 also allows the patient 104 torequest appointments from a calendar that is preferably reviewed andfurther processed by an office staff member.

FIG. 2 illustrates a flow diagram 200 showing the healthcare relatedservices provided by the HCMS 112 in the environment shown in FIG. 1,according to an embodiment of the present invention. Initially, in step201, the HCMS 112 may receive a call from a patient 104 desiringhealthcare services. In the next step 202, unique identification data ofthe patient 104, which in this example is the telephone number used bythe patient 104 to make the call, may be automatically retrieved by HCMS112 to match against the identification data stored in the database 114to initially check if the patient 104 is registered with the system. Inthe next step, 203 it may be determined whether there is a match betweenthe phone number and the unique identification data stored in thedatabase 112. If the phone number matches with the unique identificationdata stored in the database 114, then the patient 104 may be consideredto be a registered patient 104, and the HCMS 112 may function to answerthe call and greet the caller with a personalized greeting such as“Hello Ms. Smith” at step 205. If there is no match, then the patient104 may initially considered to be not registered, and at step 204, theHCMS 112 functions to answer the call and greets the patient 104 with ageneric greeting. In a preferred embodiment, the HCMS 112 may receivethe call automatically with an introductory greeting message using anInteractive Voice Response (IVR) technology. As known to one skilled inthe art, IVR is a technology that allows a computer to interact withhumans through the use of voice and dual tone multi-frequency (DTMF)keypad inputs. IVR systems can respond with prerecorded or dynamicallygenerated audio to further direct users on how to proceed. In oneembodiment, the call may be received by playing back a speech filepreferably stored on the hard drive 120. Alternatively, an operator maybe employed to answer the call and greet the caller via the HCMS 112.Then, at step 206, the patient 104 may be prompted to answer an initialscreening of health related questions to determine if it is a truehealth emergency. The initial screening of health related questions maybe asked by an operator or it may be an automated system with a set ofpre-recorded questions by playing back a speech file stored on the harddrive 120. Such topics of questions may include, but are not limited to,medical conditions relating to burns, bleeding, high fever, and cardiacarrest, etc. In the next step 208, an initial decision may be madewhether the patient 104 is critically ill to be a true health emergencybased on the answers to the initial screening of questions. In theinstance where a triage health care professional is triaging the calls,the individual may determine the nature and extent of the emergency. Ifit is determined to be a true emergency, then the patient 104 isinstructed to hang up and dial the emergency response telephone number“911” at step 210. Alternatively, if the patient 104 feels that the callis regarding a true medical emergency, then the patient 104 isautomatically instructed by the HCMS 112 to hang up and dial “911.” Inthe instance where no triage health care professional is triaging thecalls, and in the event of a true medical emergency, then the patient104 is automatically instructed by the system to hang up and dial “911”at step 210. At the next step 211, it is determined whether the patientchose to dial “911”. If at step 211 it is determined that the patient104 chose to dial “911”, then the call is terminated at step 212. It isnoted that the call can be terminated either by the HCMS 112 or thepatient 104. If at step 211 it is determined that the recognizedregistered patient 104 chooses not to dial “911”, then the methodproceeds to step 224 to retrieve the identified patient's 104 profileinformation stored in the database 114. Also, if at step 211 it isdetermined that the initially unrecognized patient 104 chooses not todial “911”, then the system will attempt to proceed to step 214 so theinitially unrecognized patient 104 may be prompted to answer a series offirst screening questions regarding registration, followed by theretrieval and transmittal of the patient's 104 health profile andcontact of the “on call” medical professional or HCP 108 for a phoneconsultation and or determination of the extent of the patient's 104condition, as will be discussed in greater detail below.

Additionally, returning back to step 208, if it is determined not to bea true health emergency at step 208, then at the next step 214 theinitially unrecognized patient 104 may be prompted by the HCMS 112 toanswer a series of first screening questions. The questions may be askedby an operator or by an automated system with a set of pre-recordedquestions by playing back a speech file stored on the hard drive 120.The questions may be configured to identify the patient 104 and todetermine how to handle the call. The questions may include, but are notlimited to, inquiring about patient's 104 name, date of birth, socialsecurity number, insurance data, telephone number etc. In step 216, thepatient's 104 answers to the questions may be used by the HCMS 112 todetermine whether the patient 104 is registered. If the patient 104 isnot registered, then the patient 104 is prompted by the HCMS 112 toregister in step 218. If the patient 104 agrees to register, then atstep 220, the patient's 104 profile information will be entered into thedatabase 114 of the HCMS 112 or participating third party systems, suchas Google Health Profile™ or Web MD™ health profile. The patient's 104profile information may then be accessible to be sent to the HCP 108provided that the HCP 108 has a compatible registered device 110 toreceive such data, at which point the HCP 108 may review the profileinformation and speak with the patient 104. In the event that thepatient 104 refuses the opportunity to register or has not providedprofile information, then no additional data will be provided to the HCP108 and the HCMS 112 will send a bill for the services deemed billable,by the HCP 108, directly to the patient 104 at step 222.

If it is determined at step 216 that the patient 104 is registered, orafter registering the patient 104 in step 220, HCMS 112 functions toidentify the patient 104 and to retrieve the identified patient's 104profile information stored in the database 114 at step 224. Then theHCMS 112 may prompt the patient 104 at step 226 to answer a series ofsecond screening questions to assess patient's 104 current healthcondition. For example, the second screening questions may include, butare not limited to, inquiring whether the patient 104 is currentlyexperiencing symptoms such a headache, cough, fever, chest pain, highblood pressure, dizziness, shortness of breath, irregular heart beatetc. An operator may listen to the spoken words of the patient 104.Alternatively, the voice recognition device 118 may convert the spokenwords of the patient 104 into text. At step 228 the HCMS 112 maydetermine how to route the call based on the answers to the secondaryscreening of questions at step 226, and the period of the time of day.Alternatively, the HCMS 112 may function to provide one or moreadvertisements as the call may be placed on a hold during the period ofdetermining on how to route the call. If at step 228, it is determinedthat the call is during office hours and can be initially handled by theoffice staff, then at step 230 and the HCP 108 is not required, the HCMS112 may connect the call to an appropriate HCP's 108 system for furtherhandling of services provided by the HCMS 112. These services to thepatients 104 include, but are not limited to, automated appointmentscheduling, reminder and confirmation, and routing the calls to officestaff during normal business hours for questions on forms, billing, etc.

At the decision state of step 228, if it is determined that it is beforeor after office hours and the patient 104 should speak to the patient'sHCP 108, and then the HCMS 112 may check the on call schedule of the HCP108, retrieve the patient's 104 profile information, and transmit thepatient's 104 profile information to the on call HCP 108 at step 232. Itis noted that the patient's 104 profile information may be transmittedto the on call HCP 108 either via one of a voice, facsimile, e-mail,video, text, etc. Immediately following the step 232, the HCMS 112 mayconnect the call to the patient's HCP'S device 110 at step 234. Then atstep 236, the recording device 116 may record the conversation betweenthe HCP 108 and the patient 104, and once the patient's HCP 108 and thepatient 104 terminates the call, the recording may be stopped. Therecorded call may be stored on the hard drive 120 and the call may beterminated at step 238.

FIG. 3 illustrates an exemplary flow diagram for providing healthcarerelated services utilizing the data collected according to the methodshown in FIG. 2, according to an embodiment of the present invention.Starting at step 302, the HCMS 112 may retrieve the recordedconversations between the HCPs 108 and the patient 104 at step 222 ofFIG. 2. In step 304, the recorded conversations may be transcribed bythe voice recognition device 118 and may be stored in the database 114corresponding to the log of the call. Note that this may be a logcontaining the complete patient 104 call record comprising the calldetails (e.g., call date, time, duration etc.), an audio recording ofthe call, and the automated voice to text transcript of the call. Aseries of log of calls along with a menu of options may then betransmitted by the HCMS 112 to the HCP 108 via the device 110 at step306. The menus of options may include, but are not limited to, thefollowing: 1) bill the call, 2) not bill the call and 3) decide later.The HCP 108 may preferably review the log of the calls and select one ofthe options provided for each call via the device 110. Upon receivingthe selection of either of the options, the HCMS 112, at step 308, mayassociate the selection with a call record of the patient 104 in thedatabase 114. In the next step 310, the HCMS 112 may retrieve all of thebillable calls from the database 114, and the patient's 104 insuranceinformation (stored either in the database 114 or another storagedevice). In the following step 312, the HCMS 112 may function to fillout the billing form, attach the voice to text transcript of thebillable call and forward them to the appropriate billing service forbilling.

It is noted that the HCP 108 may be the patient's primary physician fromthe primary practice or an on-call physician. In another embodiment,after review of the transcript between the patient 104 and the on-callphysician, the patient's primary physician may need to clarify or alterthe other HCP's healthcare advice to the patient and may contact thepatient directly to give his or her own healthcare advice thus providingan audit of the on call advice given. In this embodiment, the patient'sprimary physician may use the HCMS 112 to optionally update the patientcall record to reflect change in advice provided to the patient 104. Inan alternate embodiment, a nurse practitioner or a physician's assistantmay review the answers provided by the patients to the initial series ofthe questions and have a discussion with the patient 104 before making adecision whether the call needs to be forwarded to the patient'sphysician or on-call physician. Even though the present applicationdescribes a voice communication between the patient 104 and the HCMS112, it is readily understood that the communication may be viaelectronic mail, text messaging, and video conferencing etc.Alternatively, a voice over internet technology (VOIP) application maypreferably be used for both the patient device 106 and the HCP device110. Some of the features of the VOIP application include, but are notlimited to, allowing the patient 104 to connect directly with his or herHCP 108 in the HCMS 112 by name without a need to know the phone numbersof the HCP 108, allowing a patient 104 to request an appointment from acalendar allowing the doctor to see the patient's 104 PHP (personalhealth profile) as soon as the call comes through, permitting the HCP108 to view their office schedule, permitting HCP 108 to change their oncall status and contact number.

FIG. 4 illustrates a block diagram of an exemplary environmentcomprising a MedXCom™ healthcare communication management system (HCMS)400 implemented by a computing device such as a server for providinghealthcare related services in accordance with an embodiment of thepresent invention. It is noted that the term MedXCom™ is a proprietarytrademark and that the elements and features of the MedXCom™ HCMS 400may include components that are available in the public domain and arenon-proprietary.

In an embodiment, the patient 104 may communicate with the MedXCom™ HCMS400 via the patient device 106. In an embodiment, the patient device 106may be a smart phone. The patient device 106 may include a patient smartphone application (PSPA) 107. The PSPA 107 permits the patient 104 totake total control of his or her medical information and communicationwith the associated HCPs 108 via the MedXCom™ HCMS 400.

The MedXCom™ HCMS 400 includes an Intelligent Voice Response (IVR)module 404, an Intelligent Call Routing (ICR) module 408, a voice mailsystem 412, a manager portal 416, a scheduling module 420, a PersonalHealth Profile (PHP) server 424, a HIPAA Compliant Secure MessageGeneration and Retrieval System (HCSMGRS) 428, a registration module432, a Patient Portal (PP) 436, a Physician Portal (PYP) 440, a SecureMessaging Module (SMM) 444, and a Follow Me Module (FMM) 448.

The patient portal (PP) 436 may comprise any suitable communicationdevice including a landline device, a wireless device or an Internetthat allows for communication with any type of consumer device accessedvia a secure web HTTPS browser connection by the patient 104. In anembodiment, the PP 436 enables a patient 104 to update his or herpersonal health profile (PHP) information, connect with the patient'sdevice 106, send and receive a Short Message Service (SMS) text messageto and from the HCP 108, send and receive a secure email to and from theHCP 108, and access and join support group meetings, blogs, and chatrooms for the HCP's 108 practice. The PP 436 also enables a patient 104to receive reports and laboratory data from the HCP 108 via the HCSMGR428. The PP 436 also allows the patient 104 to upload medical reports,laboratory results, and other medical information that they havecollected over the years, and store them securely on the PHP server 424.This archived information can then be retrieved and reproduced by thepatient 104 at any time or transmitted to the HCP 108 via securemessaging, or in an emergency directly to his or her HCP's device 110.

After the MedXCom™ HCMS 400 receives a call from the patient 104, the PP436 may route the call to the registration module 432. The registrationmodule 432 is a program on the MedXCom™ HCMS 400 that maintainsregistration data regarding patients 104. If there is more than oneperson registered at a given number, then the registration module 432may prompt the patient 104 for the last four digits of the socialsecurity number. Once the registration is confirmed then the call may berouted. As discussed above, if the caller is not registered then theregistration module 432 may prompt the patient 104 to register. Theregistration module 432 confirms that the patient 104 when theregistration process is complete. If the patient 104 is not registeredand refuses to go through the registration process, then the patient 104may be routed as an unregistered patient 104 and there will be limitedor no information available about that patient 104.

The Intelligent Call Routing (ICR) module 408 is a program on theMedXCom™ HCMS 400 for handling and routing the calls from the patient104 via, for example, the Legacy office PBX or a MedXCom™ PBX. TheMedXCom™ PBX is a proprietary private branch exchange telephone systemthat includes certain embodiments of the invention as described herein.The patient 104 may instruct the ICR module 408 to leave a message on avoice mail system 412. The voice mail may be logged and displayed by themanager portal 416 for retrieval and to view retrieval status. Themanager portal 416 is a program on the MedXCom™ HCMS 400 for managingthe status of calls and the retrieval of calls. The voice mail messagemay also be transcribed and available to be viewed on the manager portal416. The manager portal 416 may be accessed by an administrator or by amanager 452. Otherwise, the patient 104 may be placed on hold and mayhear directed advertisements, which may generate revenue for the HCP108.

The ICR module 408 may route the call to the Interactive Voice mailResponse (IVR) module 404. The IVR module 404 is a program on theMedXCom™ HCMS 400 for responding to the voicemail message from thepatient 104. The IVR module 404 includes a Call Routing Module (CRM)405. The CRM 405 is a program within the IVR module 404 which mayidentify the patient 104 by name and their last call, “Hello Mrs. Smith,I see you called yesterday and spoke with Wanda. Would you like to speakwith her again today or can I help you with something else.” The CRM 405may direct the patient 104 to a specific extension of an office staffmember by name or number or the CRM 405 may allow the patient 104 tochose to speak to a live receptionist who is either in the office or onewho is provided by the MedXCom™ HCMS 400 and is off site and shared bymany practices. Either of these live operators may schedule appointmentsby connecting to the scheduling module 420.

The scheduling module 420 is a program on the MedXCom™ HCMS 400 forscheduling appointments with the HCP 108 and for sending remindermessages to the patient 104 via the Automated Appointment Reminder andConfirmation (AARC) system 421 from the scheduling module 420. The AARC421 is an application within the scheduling module 420 that maintainsand sends appointment reminders to the patient 104. The AARC 421 maysend a message to the patient 104 via SMS text, secure email, or a voiceIVR confirmation system which will call the patient 104 at home and waitfor a prompted response to either confirm or change a previouslyscheduled appointment. The patient 104 may also opt to respond to theSMS text or email to confirm or change an appointment.

The patient 104 may opt to pay a balance due and can do so from the IVRmodule 404 and connect to a legacy billing and practice managementmodule (LBPM) 456 through an application programming interface (API).The patient 104 may also choose to schedule an appointment from the IVRmodule 404 and connect to a LBPM 456 through an API. The LBPM 456 may belinked to the registration module 432 via the API.

In an embodiment, if a patient 104 calls before or after normal businesshours, the patient 104 may be asked to state his or her name and reasonfor calling as well as to verify their call back number (just in case itis not the same as the number they are calling from nor their homenumber from which they were identified). The patient 104 may be routedto a module for playing advertisements while the patient 104 is on hold,e.g., Directed Ads On Hold™, while the MedXCom™ HCMS 400 connects to theon call schedule of the HCP 108. The covering doctor or HCP 108 may beidentified and the HCP's 108 Follow Me Mode may be activated. In anembodiment, the Follow Me Mode is an application on a Follow Me Module(FMM) 448. The FMM 448 is a program on the MedXCom™ HCMS 400 forestablishing contact with an HCP 108 via a smart phone application orprovider device 110.

Based upon the Follow Me Mode preferences, which may include thepersonal preference information of an HCP 108, the number listed for thepreference during the time is called. If the number is not answered, theFMM 448 will search out the HCP 108 using the predefined sequence ofnumbers to call, as defined in the Follow Me Mode preferences. If theHCP 108 is at a number other than his or her smart phone app or providerdevice 110, then the MedXCom™ HCMS 400 will call that number and connectto the HCP 108. If, however, the HCP 108 is using their provider device110, then a VOIP call may be connected to that device 110. Using the PHPentered by the patient 104 at an earlier date and retrieved from a PHPserver 424, the PHP data is sent to the HCP's device 110. In anembodiment, a PHP server 424 is a server that stores and maintains apatient's 104 PHP data. The PHP data, which is stored on the PHPdatabase 425, may be mined based on what information that the HCP 108believes is important in order to take care of their particular patient104.

The patient's 104 PHP data may be entered in the MedXCom™ HCMS 400 viathe patient's device 106 via the PP 436 for storage on both the patientsmart phone app (PSPA) 107 and the PHP server 424. The PSPA 107 is anapplication on the patient's device 106. In doing so, the patient 104controls who may have access to the patient's 104 PHP data via apermission system located on both the PSPA 107 and the PP 436. When thepatient 104 calls an HCP 108, the PHP data may be sent to thephysician's smart phone application (PYSPA) 111 and data mined forrelevant info for that particular type of HCP 108, and the mined infomay be sent to the PYSPA 111 for display of that critical medicalinformation at the time of the emergency phone call. The PYSPA 111 is anapplication that executes on the physician device 110 and, along withthe PYP 440, serves as a mobile hub of communications for the HCP 108.In an embodiment, the PHP data can also be printed easily or access canbe given to a non-participating practice for printing or transfer to,for example, and emergency room.

The patient 104 may also upload PHP data and information on to the PP436, and information from the PP 436 can be accessed via the PSPA 107 orthe patient device 106. The PSPA 107 and the patient device 106 may beused to update the PHP and any changes to the PHP made via the PP 436may be sent to the PSPA 107 to update the cache memory for the PHP. ThePHP data may be sent to the provider's device 110 during an emergencycall. A meet me conferencing with HCPs 108 can occur via the PSPA 107.The patient 104 may communicate with other patients 104 via a SupportGroup/Meetings/Blogs/Chat Module. The patient 104 may exchange textmessages with their HCPs 108 via the Secure Message Module (SMM). Emailsmay be sent to the PP 436 for review. The patient 104 may use the PSPA107 via a VOIP call into the MedXCom™ HCMS 400 directly without usingthe actual cell phone via a phone call. Since the application isregistered to only one patient 104, the MedXCom™ HCMS 400 may identifythe VOIP call from that application as one coming from that registeredpatient 104.

The patent's 104 PHP data may be displayed on the PYSPA 111 on theprovider device 110. The MedXCom™ HCMS 400 may then route the call tothe HCP 108. In either case, the HCP 108 may hear the name and messageleft for them by the patient 104 when the call is connected. TheMedXCom™ HCMS 400 may give the HCP 108 the option to: “Accept” the calland be connected to the patient 104; select “Call Back” and then havethe MedXCom™ HCMS 400 call back for a defined period of time andreconnect them to the patient 104; or defer the call and they can callthe patient 104 back when the HCP 108 finds the time. Once connected,the calls may be recorded and transcribed. At the end of the call, theHCP 108 may be given the opportunity to dictate an addendum to the callwhich he or she may feel is appropriate for documentation but notspecifically for discussion with the patient 104. This transcription maybe queued for transcription and billing submission for a telephoneconsultation. Calls with their transcriptions and billing info may besent to the manager portal 416 so that they can be submitted to theinsurance company for reimbursement. In an embodiment, the recordedconversation may be transmitted to the patient 104. Also, thetranscription of the recorded conversation may be transmitted to thepatient 104.

After the call, the HCP 108 has the option to send a follow up email ortext message from the PYSPA 111 to the patient 104 regardinginstructions related to the call. These messages may be such things asbasic wound care instructions or a reiteration to go to the nearestemergency room for treatment. This message may be sent from the HIPAACompliant Secure Messaging Generation and Retrieval System (HCSMGRS) 428via Short Message Service (SMS) text message or secure email. TheHCSMGRS 428 is a program on the MedXCom™ HCMS 400 for generating andretrieving messages in compliance with Health Insurance Portability andAccountability Act (HIPAA) laws. The HCP 108 may need to prescribemedicine to the patient 104 based on the phone conversation. The HCP 108may send the prescription directly via an electronic prescriptionprogram such as ePrescribe™ 111A, or to the pharmacy 472 right from alink on their PYSPA 111 or provider device 110.

The Physicians Portal (PYP) 440 is the communication and messaging hubfor the entire system for the HCP 108. Hospitals 464 and laboratories460 can send reports and data directly to the PYP 440 for review, andother doctors 468 can collaborate by sending reports and data to eachother. The reports, data, and messages may be displayed on the dashboard110D, and may display the status of the message as unread, read,forwarded or cc′d. A dashboard 110D is a tool on the physician'scomputer 110A or on the physician device 110 that enables the HCP 108 toview and manage data. In addition, calls that have entered the MedXCom™HCMS 400 may have been recorded and available for playback. This mayinclude a log of all the calls with the recording files attached and maybe accessible for review at the click of an icon on the PYSPA 111 or theprovider device 110. The transcriptions of the calls and the initialmessages may be displayed on the PYSPA 111 or the provider device 110 ina time sequence for review. The status of each call may be displayed incase, for example, any calls went unanswered. In an embodiment, the PYP440 may display the daily patient's 104 schedule for review via aconnection to the legacy practice management system. The HCP 108 mayalso change or review the On Call Schedule directly from this screen.The HCP 108 may also change his or her Follow Me Mode status and updateas needed. All email communications to or from the SMM 444 may bereviewed and sent from an email tab within the PYP 440. Any providerconference bridge conversations may be displayed as a recording or atranscription in a log on the PYP 440.

HCP 108 may communicate directly with the MedXCom HCMS 400 via the PYPSA111. The HCP 108 may access and change his or her FMM status from thePYPSA 111. The HCP 108 may access and update or change his or her oncall schedule by accessing the On Call Scheduling Module (OCSM) fromtheir PYPSA 111. Most importantly, when a call from a patient 104 comesin, the patient's 104 PHP data may be sent to and displayed on the PYSPA111 when it is needed most—at the time of the patient 104 contact duringthe call. The PYSPA 111 allows for electronic prescription applicationssuch as ePrecribe™ 111A to send prescriptions to the pharmacy 472 forthe patient 104 based on the listed pharmacy 472 in the patient's 104PHP. The HCP 108 may also send an email confirmation or reminder to thepatient 104 in order to ensure or reinforce understanding of what wasdiscussed with the patient 104 during the previous call. All calls maybe recorded for quality review and may be transcribed for archivaldocumentation or billing purposes. In an embodiment, the recordedconversation may be transmitted to the patient 104. Also, thetranscription of the recorded conversation may also be transmitted tothe patient 104. This may enable the patient 104 to confirm anyimportant points that were made by the HCP 108 during the call. The HCP108 may also make an addendum to the call for a personal reminder or aclarification of why certain things were said or to emphasize a point(such as the patient 104 continues to smoke despite repeatedly beingtold to stop smoking). Through the PYSPA 111, the provider or HCP 108can access the Provider's Contact List (PCL) and contact any otherprovider or HCP 108 on the HCMS 112 directly via VOIP, and share dataregarding their patient 104 in real time.

The computer system 500 may further include a network interface device522. The computer system 500 also may include a video display unit 510(e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), analphanumeric input device 512 (e.g., a keyboard), a cursor controldevice 514 (e.g., a mouse), and a signal generation device 520 (e.g., aspeaker).

A drive unit 516 may include a computer-readable medium 524 on which isstored one or more sets of instructions embodying any one or more of themethodologies or functions described herein. The instructions may alsoreside, completely or at least partially, within the main memory 504and/or within the processing device or processor 502 during executionthereof by the computer system 500, the main memory 504 and theprocessor 502 also constituting computer-readable media. Theinstructions may further be transmitted or received over a network viathe network interface device 522.

While the computer-readable storage medium 524 is shown in an exemplaryembodiment to be a single medium, the term “computer-readable storagemedium” should be taken to include a single non-transitory medium ormultiple non-transitory media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore sets of instructions. The term “computer-readable storage medium”shall also be taken to include any medium that is capable of storing,encoding or carrying a set of instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present invention. The term “computer-readablestorage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, optical media, and magnetic media.

In the above description, numerous details are set forth. It will beapparent, however, to one of ordinary skill in the art having thebenefit of this disclosure, that embodiments of the invention may bepracticed without these specific details. In some instances, well-knownstructures and devices are shown in block diagram form, rather than indetail, in order to avoid obscuring the description.

Some portions of the detailed description are presented in terms ofalgorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like.

Embodiments of the invention also relate to an apparatus for performingthe operations herein. This apparatus may be specially constructed forthe required purposes, or it may comprise a general purpose computerselectively activated or reconfigured by a computer program stored inthe computer. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding floppy disks, optical disks, CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring electronic instructions.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct a more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear from the description below.In addition, the present invention is not described with reference toany particular programming language. It will be appreciated that avariety of programming languages may be used to implement the teachingsof the invention as described herein.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

It is to be understood that the exemplary embodiments are merelyillustrative of the invention and many variations of the above-describedembodiments can be devised by one skilled in the art without departingfrom the scope of the invention. It is therefore intended that all suchvariations be included within the scope of the following claims andtheir equivalents.

Some portions of the detailed descriptions above are presented in termsof algorithms and symbolic representations of operations on data bitswithin a computer memory. These algorithmic descriptions andrepresentations are the means used by those skilled in the dataprocessing arts to most effectively convey the substance of their workto others skilled in the art. An algorithm is here, and generally,conceived to be a self-consistent sequence of steps leading to a desiredresult. The steps are those requiring physical manipulations of physicalquantities. Usually, though not necessarily, these quantities take theform of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. It hasproven convenient at times, principally for reasons of common usage, torefer to these signals as bits, values, elements, symbols, characters,terms, numbers, or the like. It should be borne in mind, however, thatall of these and similar terms are to be associated with the appropriatephysical quantities and are merely convenient labels applied to thesequantities. Unless specifically stated otherwise, as apparent from thefollowing discussion, it is appreciated that throughout the description,discussions utilizing terms such as “identifying,” “creating,”“associating,” “maintaining,” “receiving,” “authenticating,”“refraining,” “identifying,” “specifying,” “determining,” “granting,”“accessing,” “as signing,” “executing,” “monitoring,” “detecting,”“requesting,” “routing”, “generating”, “recording”, “transmitting”,“transcribing”, and “adjusting,” or the like, refer to the action andprocesses of a computer system, or similar electronic computing device,that manipulates and transforms data represented as physical(electronic) quantities within the computer system's registers andmemories into other data similarly represented as physical quantitieswithin the computer system memories or registers or other suchinformation storage, transmission or display devices.

Embodiments of the present invention also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, or it may be a general purposecomputer system selectively programmed by a computer program stored inthe computer system. Such a computer program may be stored in a computerreadable storage medium, such as, but not limited to, any type of diskincluding optical disks, CD-ROMs, and magnetic-optical disks, read-onlymemories (ROMs), random access memories (RAMs), EPROMs, EEPROMs,magnetic disk storage media, optical storage media, flash memorydevices, other type of machine-accessible storage media, or any type ofmedia suitable for storing electronic instructions, each coupled to acomputer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general purposesystems may be used with programs in accordance with the teachingsherein, or it may prove convenient to construct a more specializedapparatus to perform the required method steps. The required structurefor a variety of these systems will appear as set forth in thedescription below. In addition, the present invention is not describedwith reference to any particular programming language. It will beappreciated that a variety of programming languages may be used toimplement the teachings of the invention as described herein.

It is to be understood that the above description is intended to beillustrative, and not restrictive. Many other embodiments will beapparent to those of skill in the art upon reading and understanding theabove description. Although the present invention has been describedwith reference to specific exemplary embodiments, it will be recognizedthat the invention is not limited to the embodiments described, but canbe practiced with modification and alteration within the spirit andscope of the appended claims. Accordingly, the specification anddrawings are to be regarded in an illustrative sense rather than arestrictive sense. The scope of the invention should, therefore, bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

1-20. (canceled)
 21. A method comprising: receiving, by a processing device, a call from a communication device associated with a patient, the communication device associated with a patient comprising a first application and having a unique identifier; associating, by the processing device, the unique identifier with a personal health profile stored in a database, wherein the personal health profile comprises medical information of the patient and an on call schedule of a first health care provider associated with the patient; determining, by the processing device, a first communication device associated with the first health care provider based on the on call schedule; transmitting, by the processing device, the personal health profile to the first communication device via an electronic communication; communicatively connecting, by the processing device, the call from the communication device associated with the patient with the first communication device associated with the first health care provider; recording a conversation between the patient and the first health care provider during the communicatively connected call from the communication device associated with the patient with the first communication device associated with the first health care provider; generating, by the processing device, a transcription based on the communicatively connected call between the patient and the first health care provider; generating, by the processing device, a completed billing form based in part on a log of the call from the communication device associated with patient; and transmitting the completed billing form and the transcription of the recorded conversation to a billing service.
 22. The method of claim 21, further comprising: generating, by the processing device, an invoice based on a log of the call from the communication device associated with patient; and transmitting the invoice to the communication device associated with the patient.
 23. The method of claim 21, further comprising: storing the recorded conversation in the database; and storing the transcription of the recorded conversation in the database.
 24. The method of claim 21, further comprising: receiving, by the processing device, an update to the transcription from at least one of the first communication device associated with the first health care provider or a second communication device associated with a second health care provider; and storing, by the processing device, the update to the transcription in association with the personal health profile.
 25. The method of claim 21, further comprising: transmitting the recorded conversation to the patient; and transmitting the transcription of the recorded conversation to the patient.
 26. The method of claim 21, further comprising: receiving, by the processing device, a message from the first communication device associated with the first health care provider, the message comprising medical information provided by the first health care provider to the patient; determining, by the processing device, that the message is in compliance with one or more US HIPAA laws; and transmitting the message to the patient.
 27. The method of claim 21, further comprising: generating, by the processing device, an appointment reminder message, the appointment reminder message comprising information to remind the patient of an appointment with at least one of the first health care provider or the second health care provider; transmitting the appointment reminder message to the patient; and receiving a confirmation message from the patient in response to the transmitted appointment reminder message.
 28. A system comprising: a database; and a processing device communicatively coupled to the database, the processing device configured to: receive a call from a communication device associated with a patient, the communication device associated with a patient having a unique identifier; associate the unique identifier with a personal health profile stored in a database, wherein the personal health profile comprises medical information of the patient and an on call schedule of a first health care provider associated with the patient; determine a first communication device of a plurality of communication devices associated with the first health care provider based on the on call schedule; transmit the personal health profile to the first communication device associated with the first health care provider via an electronic communication; communicatively connect the call from the communication device associated with the patient with the communication device associated with the first health care provider; record a conversation between the patient and the first health care provider during the communicatively connected call from the communication device associated with the patient with the first communication device associated with the first health care provider; generate a transcription based on the communicatively connected call between the patient and the first health care provider; generate a completed billing form based in part on a log of the call from the communication device associated with patient; and transmit the completed billing form and the transcription of the recorded conversation to a billing service.
 29. The system of claim 28, wherein the processing device is further configured to: generate an invoice based on a log of the call from the communication device associated with patient; and transmit the invoice to the communication device associated with the patient.
 30. The system of claim 28, wherein the processing device is further configured to: store the recorded conversation in the database; and store the transcription of the recorded conversation in the database.
 31. The system of claim 28, wherein the processing device is further configured to: receive an update to the transcription from at least one of the first communication device associated with the first health care provider or a second communication device associated with a second health care provider; and store the update to the transcription in association with the personal health profile.
 32. The system of claim 28, wherein the processing device is further configured to: transmit the recorded conversation to the patient; and transmit the transcription of the recorded conversation to the patient.
 33. The system of claim 28, wherein the processing device is further configured to: receive a message from the communication device associated with a health care provider, the message comprising medical information from the first health care provider to the patient; determine that the message is in compliance with one or more US HIPAA laws; and transmit the message to the patient.
 34. The system of claim 28, wherein the processing device is further configured to: generate an appointment reminder message, the appointment reminder message comprising information to remind the patient of an appointment with at least one of the first health care provider or the second health care provider; transmit the appointment reminder message to the patient; and receive a confirmation message from the patient in response to the transmitted appointment reminder message.
 35. A non-transitory computer readable storage medium including instructions that, when executed by a processing device, cause the processing device to: receive, by the processing device, a call from a communication device associated with a patient, the communication device associated with the patient having a unique identifier; associate, by the processing device, the unique identifier with a personal health profile stored in a database, wherein the personal health profile comprises medical information of the patient and an on call schedule of a first health care provider associated with the patient; determine, by the processing device, a first communication device of a plurality of communication devices associated with the first health care provider based on the on call schedule; transmit the personal health profile to the first communication device associated with the first health care provider via an electronic communication; communicatively connect the call from the communication device associated with the patient with the communication device associated with the first health care provider; record a conversation between the patient and the health care provider during the communicatively connected call from the communication device associated with the patient with the first communication device associated with the first health care provider; generate a transcription based on the communicatively connected call between the patient and the first health care provider; generate, by the processing device, a completed billing form based in part on a log of the call from the communication device associated with patient; and transmit the completed billing form and the transcription of the recorded conversation to a billing service.
 36. The non-transitory computer readable storage medium of claim 35, the processing device to: generate, by the processing device, an invoice based on a log of the call from the communication device associated with patient; and transmit the invoice to the communication device associated with the patient.
 37. The non-transitory computer readable storage medium of claim 35, the processing device to: store the recorded conversation in the database; and store the transcription of the recorded conversation in the database.
 38. The non-transitory computer readable storage medium of claim 35, the processing device to: receive an update to the transcription from at least one of the first communication device associated with the first health care provider or a second communication device associated with a second health care provider; and store the update to the transcription in association with the personal health profile.
 39. The non-transitory computer readable storage medium of claim 35, the processing device to: transmit the recorded conversation to the patient; and transmit the transcription of the recorded conversation to the patient.
 40. The non-transitory computer readable storage medium of claim 35, the processing device to: receive, by the processing device, a message from the first communication device associated with the first health care provider, the message comprising medical information from the first health care provider to the patient; determine, by the processing device, that the message is in compliance with one or more US HIPAA laws; and transmit, the message to the patient.
 41. The non-transitory computer readable storage medium of claim 35, the processing device to: generate, by the processing device, an appointment reminder message, the appointment reminder message comprising information to remind the patient of an appointment with the first health care provider; and transmit the appointment reminder message to the patient. 